UAV communication enhancement module

ABSTRACT

Embodiments for a method for enhancing communication for one or more unmanned aerial vehicles (UAVs) are also disclosed. The method includes receiving, at a first communication enhancement module of a first UAV, a STANAG 4586 message from an upstream module. The STANAG 4586 message indicates a MUCS as its destination. A multi-hop path to the MUCS via at least one other communication enhancement module is identified. It is determined whether a point-to-point wireless link or the multi-hop route is a better path to the MUCS. If a point-to-point wireless link is a better path, the message is sent over the point-to-point wireless link to the MUCS. If the multi-hop route is a better path, the message is modified to create a modified message having a format corresponding to the communication enhancement modules. The modified message is then sent to the other communication enhancement module(s) on the multi-hop path.

BACKGROUND

The Unmanned Aerial Vehicle (UAV) communication standard STANAG 4586allows multiple UAVs to interoperate with a single UAV control system(UCS). Enabling a single UCS to interoperate with multiple UAVsincreases command and control efficiency and flexibility in operatingUAVs. Because of the interoperability advantages of STANAG 4586, manycurrent and future UAVs are/will be compatible with the standard.

A UCS that is compliant with STANAG 4586 can be referred to as amulti-UAV control system (MUCS). STANAG 4586 provides for communicationbetween a MUCS and a UAV via a point-to-point wireless link between theUAV and the UCS. If multiple UAVs are being controlled by the MUCS, eachof the multiple UAVs has a distinct point-to-point wireless link betweenthat UAV and the MUCS. The point-to-point links used with STANAG 4586,however, can suffer from severe bandwidth degradation in certainenvironments due to weather, geography, and/or enemy jamming. Because ofthis, there is a need to improve the robustness and reliability ofcommunications for UAVs using the STANAG 4568 standard.

BRIEF DESCRIPTION

Embodiments for a communication enhancement module for an unmannedaerial vehicle (UAV) or a multi-UAV control system (MUCS) are disclosed.The communication enhancement module includes a computer readable mediumhaving instructions thereon. The instructions, when executed by one ormore processing devices, cause the one or more processing devices toreceive a STANAG 4586 message from an upstream module, the STANAG 4586indicating that a second UAV or a MUCS is its destination. Theinstructions also cause the one or more processing devices to identify amulti-hop path to the second UAV or the MUCS via at least one othercommunication enhancement module in a first UAV. The instructions alsocause the one or more processing devices to determine whether apoint-to-point wireless link or the multi-hop route is a better path tothe second UAV or the MUCS. If the point-to-point wireless link is thebetter path, the one or more processing devices send a message based onthe STANAG 4586 message over the point-to-point wireless link to thesecond UAV or the MUCS. If the multi-hop path is the better path, theone or more processing devices adapt the STANAG 4586 message to create amodified message having a format corresponding to the communicationenhancement modules; and send the modified message to a communicationenhancement module of the first UAV for directing toward the second UAVor the MUCS.

Embodiments for a method for enhancing communication for one or moreunmanned aerial vehicles (UAVs) are also disclosed. The method includesreceiving, at a first communication enhancement module of a first UAV ofthe one or more UAVs, a STANAG 4586 message from an upstream module inthe first UAV. The STANAG 4586 message indicates a MUCS as itsdestination. A multi-hop path to the MUCS via at least one othercommunication enhancement module of at least one other UAV isidentified. The method also includes determining whether apoint-to-point wireless link or the multi-hop route is a better path tothe MUCS. If a point-to-point wireless link is a better path, a messagebased on the STANAG 4586 message is sent over the point-to-pointwireless link to the MUCS. If the multi-hop route is a better path, theSTANAG 4586 message is modified to create a modified message having aformat corresponding to the communication enhancement modules, and themodified message is sent to the at least one other communicationenhancement module on the multi-hop path for directing toward the MUCS.

Embodiments for an unmanned aerial vehicle (UAV) including a propulsionsystem to propel the UAV in flight, and a communication enhancementmodule. The communication enhancement module includes one or moreprocessing devices and a computer readable medium coupled to the one ormore processing devices. The computer readable medium includesinstructions thereon. The instructions, when executed by the one or moreprocessing devices, cause the one or more processing devices to receivea STANAG 4586 message from an upstream module. The STANAG 4586 indicatesthat a MUCS is its destination. The instructions also cause the one ormore processing devices to identify a multi-hop path to the MUCS via atleast one other communication enhancement module in another UAV. Theinstructions also cause the one or more processing devices to determinewhether a point-to-point wireless link or the multi-hop route is abetter path to the MUCS. If the point-to-point wireless link is thebetter path, a message based on the STANAG 4586 message is sent over thepoint-to-point wireless link to the MUCS. If the multi-hop path is thebetter path, the STANAG 4586 message is adapted to create a modifiedmessage having a format corresponding to the communication enhancementmodules. The modified message is then sent to a communicationenhancement module of the other UAV for directing toward the MUCS.

DRAWINGS

Understanding that the drawings depict only exemplary embodiments andare not therefore to be considered limiting in scope, the exemplaryembodiments will be described with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 is a block diagram of an example system including a multi-UAVcontrol system (MUCS) and a plurality of UAVs that have communicationenhancement modules therein;

FIG. 2 is a block diagram of a portion of the system of FIG. 1, showingan example MUCS and UAVS having communication enhancement modulestherein;

FIG. 3 is a flow diagram of an example method of enhancing communicationfor a plurality of UAVs using the communication enhancement modules ofFIG. 2;

FIG. 4 is a block diagram of an example UAV having a software toolcommunication enhancement module therein; and

FIG. 5 is a block diagram of an example UAV having a hardware appliancecommunication enhancement module therein.

DETAILED DESCRIPTION

The subject matter described herein provides for a communicationenhancement module that can be added to a plurality of UAVs and to aMUCS to improve the robustness and reliability of UAV communications inthe face of degraded bandwidth wireless links. The communicationenhancement module exploits the common communication protocol used bySTANAG 4586 compliant UAVs and MUCS to interact with the UAVs and MUCSas a bump-in-the wire or bump-in-the-stack module that enhances thecommunication capabilities of the UAVs and MUCS. The communicationenhancement module interacts with its UAV or MUCS using the STANAG 4586protocol, enabling the communication enhancement module to be added toany new or existing STANAG 4586 compliant UAV or MUCS. Accordingly, thecommunication enhancement module is configured to be added to acommercial off the shelf (COTS) UAV infrastructure and can provideenhanced communication capabilities thereto.

FIG. 1 is a bock diagram of an example system 100 for enhancingcommunication among a plurality of unmanned aerial vehicles (UAVs)102-106. System 100 includes a first UAV 102, a second UAV 104, and athird UAV 106, each of which are communicatively coupled to, andcontrolled by, a multi-UAV control system (MUCS) 108. The MUCS 108controls the UAVs 102-106 by sending STANAG 4586 messages to the UAVs102-106. The UAVs 102-106 receive the STANAG 4586 messages and takeaction as directed by the commands in the STANAG 4586 messages. The UAVs102-106 can also send STANAG 4586 messages to the MUCS 108 tocommunicate information back to the MUCS 108. A STANAG 4586 message is amessage that conforms to a STANAG 4586 standard, such as edition 3 ofthe STANAG 4586 standard published on Nov. 9, 2012 by the NATOStandardization Agency, which is hereby incorporated herein byreference. For example, a STANAG 4586 message can be any of the Generic(Common) DLI messages in section 4 of Appendix 1 of Annex B of STANAG4586.

Each UAV 102-106 and the MUCS 108 includes a respective communicationenhancement module 112-118. Each communication enhancement module112-118 is a software tool or hardware-and-software appliance thatinteracts with other components of the UAV or MUCS in which the module112-118 is installed to provide enhanced communication capabilities forthe UAV or MUCS.

Each UAV 102-106 can be communicatively coupled to the MUCS 108 via arespective point-to-point wireless link 110 between the respective UAV102-106 and the MUCS 108 in accordance with the STANAG 4586 standard. Inan example, the point-to-point wireless link 110 is a command andcontrol (C2) and/or payload data link for the UAV 102-106. In additionto the point-to-point wireless links 110 with the MUCS 108, thecommunication enhancement modules 102-106 enable each UAV 102-106 toform a point-to-point wireless link 111 with other UAVs 102-106 that arewithin communication range. A point-to-point wireless link between twoUAVs 102-106 is also referred to herein as a UAV-to-UAV link, and apoint-to-point wireless link between a UAV 102-106 and the MUCS 108 isalso referred to herein as a UAV-to-MUCS link.

The UAV-to-UAV links 111 enable multi-hop routes between a UAV 102-106and the MUCS 108, instead of having only UAV-to-MUCS link with the MUCS108 as supported by the STANAG 4586 standard. The combination of theUAV-to-UAV links 111 and the UAV-to-MUCS links 110 form a network amongthe UAVs 102-106 and MUCS 108. The network provides a counter tobandwidth degradation in the point-to-point links 110 with the MUCS 108,by enabling a first UAV 102 to communicate with the MUCS 108 via amulti-hop route that uses the point-to-point link 110 between anotherUAV 104, 106 and the MUCS 108 to communicatively couple the first UAV102 to the MUCS 108.

Notably, the communication enhancement modules 112-118 enable UAV-to-UAVlinks 111 to be formed between the UAVs 102-106 while still allowing theUAVs 102-106 to be fully compliant with STANAG 4586, which does notprovide for such UAV-to-UAV links 111. The communication enhancementmodules 112-118 do so by controlling both ends of the communicationlinks 110, 111 for corresponding UAVs 102-106. To control both ends ofthe communication links 110, 111, a respective communication enhancementmodule is provided on each end of each link 110, 111 that is controlled.For example, for the communication link 110 between the MUCS 108 and thefirst UAV 102, a first communication enhancement module 118 is includedin the MUCS 108 for the first end of the communication link 110, and asecond communication enhancement module 112 is included in the first UAV102 for the second end of the link 110. Similarly, for the link 111between the first UAV 102 and a second UAV 104, the second communicationenhancement module 112 is used for the first end of the link 111 and athird communication enhancement module 114 in the second UAV 104 is usedfor the second end of the link 111. By providing a communicationenhancement module 112-118 at each of MUCS 108 and UAVs 102-106, apoint-to-point link can be formed between any two of the MUCS/UAVs102-106.

The communication enhancement modules 112-116 included in theirrespective UAVs 102-106 can be physically disposed in or on the body oftheir UAV 102-106, so that the communication enhancement modules 112-116travel with their UAV 102-106 as it flies around. The MUCS 108 and itscorresponding communication enhancement module 118 can be disposed atany appropriate location including on the ground or in an aircraft. Inan example, all components of the MUCS 108 can be disposed at a commonlocation or the components of the MUCS 108 can be distributed acrossmultiple locations.

Although three UAVs 102-106 are included the example with reference toFIG. 1, it should be understood that the number of UAVs controlled by aMUCS 108 and in which communication enhancement modules 112-116 areincluded therein is not limited by the subject matter described herein.Accordingly, fewer or more than three UAVs 102-106 can be included insystem 100. Moreover, all of the UAVS controlled by a MUCS 108 can, butneed not, include a respective communication enhancement module. Any UAVthat does not have a communication enhancement module can stillcommunicate with the MUCS 108 using STANAG 4586 over its UAV-to-MUCSlink, but will not have the enhanced communication advantages enabled bythe communication enhancement modules. Thus, a set of UAVs controlled bya MUCS 108 can include both UAVs that do include communicationenhancement modules and one or more UAVs that do not include acommunication enhancement module.

FIG. 2 is a block diagram of a portion of system 100 showing the MUCS108, a first UAV 102, and a second UAV 104. In the situation shown, aUAV-to-MUCS link 110 is established between the MUCS 108 and the firstUAV 102, and a UAV-to-UAV link 111 is established between the first UAV102 and the second UAV 104. There is no UAV-to-MUCS link establishedbetween the second UAV 104 and the MUCS 108. Communications between theMUCS 108 and the first UAV 102 occur over the UAV-to-MUCS link 110.Communications between the MUCS 108 and the second UAV 104 occur over aroute including both the UAV-to-MUCS link 110 and the UAV-to-UAV link111.

Each of the MUCS 108, the first UAV 102, and the second UAV 104 includea respective communication enhancement module 118, 112, 114. Thecommunication enhancement modules 118, 112, 114, coordinate with oneanother to provide the route between the MUCS 108 and the second UAV 104via the first UAV 102.

Each of the MUCS 108, the first UAV 102, and the second UAV 104 includeone or more data terminals 206, 202, 204 for generating the physicallayer for the wireless link(s) 110, 111 of their corresponding device.The data terminal(s) 206, 202, 204 can generate and receive therespective wireless signal to/from their corresponding UAV/MUCS 102,104, 108. The wireless signal for each communication link 110, 111 canhave any suitable physical layer protocol in any suitable frequencyrange, such as those commonly used with STANAG 4586. Multiple dataterminals 202, 204, 206 can be included in a MUCS 108 or UAV 102, 104for wireless communication over multiple frequencies or communicationprotocols.

Each UAV/MUCS 102, 104, 108 also includes a main processing module 208,210, 212 (e.g., air vehicle element, UCS element). The main processingmodule 208, 210, 212, generates and receives STANAG 4586 messages forcommunication over the wireless link(s) 110, 111 with the MUCS or UAV102, 104, 106. The main processing module 208, 210, 212 can also performgeneral purpose processing for the MUCS/UAV 102, 104, 108. For example,the main processing module 208 in the MUCS 108 can operate a UAV controlsystem for the UAVs 102, 104 and can generate commands to-be-sent to theUAVs 102, 104 to effectuate such controls. The main processing modules210, 212 in the UAVs 102, 104 can include a vehicle specific module thatperform the avionic processing for the UAV and take action in responseto commands received from the MUCS 108. Each MUCS/UAV 102, 104, 108 canalso include other elements that interact with the main processingmodules 208, 210, 212 to perform tasks as desired by the MUCS 108 andthe UAVs 102, 104. These other elements can include one or moreinput/output (I/O) devices 214 at the MUCS 108 for receiving input fromand providing output to a user. The I/O device(s) 214 can include anysuitable I/O device such as a keyboard, display screen, touchscreen,mouse, touchpad, microphone, etc. The MUCS 108 can also include a launchand recovery element 216 for generating commands for directing the UAVs102, 104 to launch and be recovered. The main processing module 208 ofthe MUCS 108 can also send and receive information to/from externallycoupled systems, such as an external C41 system 217. The UAVs 102, 104,can include one or more payload elements 218, 220 which perform tasksfor the UAV 102, 104, such as a video camera for capturing video.

The communication enhancement module 112, 114, 118 of each UAV/MUCS 102,104, 108 is disposed in the communication path between the one or moredata terminals 202, 204, 206 and the main processing module 208, 210,212 of that UAV/MUCS 102, 104, 108. Thus, the communication enhancementmodule 112, 114, 118 is coupled to the one or more data terminals 202,204, 206 and to the main processing module 208, 210, 212 of its UAV MUCS102, 104, 108. If a UAV/MUCS 102, 104, 108 has multiple data terminals202, 204, 206, the communication enhancement module 112, 114, 118 of theUAV/MUCS 102, 104, 108 can be coupled to each of the multiple dataterminals 202, 204, 206 to provide the communication enhancements forall the corresponding communication links, or the communicationenhancement module 112, 114, 118 can be coupled to a subset of themultiple data terminals 202, 204, 206.

In the outbound direction, each main processing module 208, 210, 212generates STANAG 4586 messages for sending to a UAV/MUCS 102, 104, 108.The main processing modules 208, 210, 212 can generate the STANAG 4586messages in accordance with STANAG 4586 based on any suitableinformation. For example, the main processing module 208 in the MUCS 108can receive inputs from the I/O device 214, wherein the inputscorrespond to commands for the first UAV 102. The main processing module208 can receive the inputs from the I/O device 214 and generate STANAG4586 messages corresponding to the commands for the first UAV 102. Asanother example, the main processing module 210 in the first UAV 102,can receive information from the payload element 218 and generate STANAG4586 messages corresponding to the information, to transmit theinformation to the MUCS 108. Similarly, the main processing module 212in the second UAV 104, can receive information from the payload element220 and generate STANAG 4586 messages corresponding to the information,to transmit the information to the MUCS 108.

In the inbound direction, each main processing module 208, 210, 212 canreceive STANAG 4586 messages and take appropriate action in response tothe STANAG 4586 message. For example, the main processing module 208 inMUCS 108 can receive a STANAG 4586 message from the first UAV 102,wherein the STANAG 4586 message contains information that was obtainedby the payload element 218 of the first UAV 102. The main processingmodule 208 of the MUCS 108 can receive this STANAG 4586 message, decodethe message, and provide information to the I/O device 214 for the I/Odevice 214 to provide as output to a user. The main processing module210 in the first UAV 102 can receive a STANAG 4586 message from the MUCS108, wherein the STANAG 4586 message contains a command for an action tobe taken by the payload element 218. The main processing module 210 ofthe first UAV 102 can receive this STANAG 4586 message, decode themessage, and command the payload element 218 in accordance with theSTANAG 4586 message.

Each communication enhancement module 112, 114, 118 can be coupledbetween the main processing module 210, 212, 208 and the data terminal202, 204, 206 of its UAV/MUCS 102, 104, 108. The communicationenhancement module 112, 114, 118 can interact with the main processingmodule 210, 212, 208 of its UAV/MUCS 102, 104, 108 to provide thecommunication enhancements for the device 102, 104, 108. In particular,the communication enhancement modules 118, 112, 114 on each end of awireless link 110, 111 cooperate to intercept STANAG 4586 messagesto-be-sent over the wireless link 110, 111 and adapt the messages toprovide the enhanced communication features. The adapted messages arethen received by the communication enhancement modules 118, 112, 114 onthe other end of the wireless link 110, 111, which undo the adaptationsto re-generate the STANAG 4586 message that was originally to-be-sent.The communication enhancement modules 118, 112, 114 then pass there-generated STANAG 4586 message on their corresponding main processingunit 208, 210, 212.

Because the communication enhancement modules 118, 112, 114 are coupledbetween the main processing module 208, 210, 212 and their correspondingdata terminal 206, 202, 204, the communication enhancement modules 118,112, 114 can intercept the STANAG 4586 messages before they are sentover the communication link 110, 111. Thus, the communicationenhancement modules 118, 112, 114 can adapt outgoing STANAG 4586messages before they are sent. Additionally, this location allows thecommunication enhancement modules 118, 112, 114 to receive the adaptedmessages before they are passed to the main processing module 210, 212,214. Thus, the communication enhancement modules 118, 112, 114 can undothe adaptations for incoming adapted messages before the messages arepassed to the main processing module 208, 210, 212. Accordingly, theposition in which the communication enhancement modules 112, 114, 118are coupled enables the adaptations to the STANAG 4586 messages to betransparent to the main processing modules 208, 210, 212.

Additionally, by interacting with the main processing modules 208, 210,212 using STANAG 4586 messages, the communication enhancement modules118, 112, 114 can be added to any MUCS 108 or UAV 102, 104, 106 that cansend and receive STANAG 4586 messages. Moreover, the components of theMUCS 108 or UAV 102, 104, 106 to which the communication enhancementmodule 118, 112, 114 is added do not require significant changes for thecommunication enhancements. Instead, the main processing unit 208, 210,212 of the MUCS 108 or UAV 102, 104, 106 can input and output STANAG4586 messages in the normal manner, merely adjusting where the STANAG4586 messages are passed to and received from. Instead of passingmessages to the data terminal 202, 204, 206, the main processing unit210, 212, 214 passes information to the communication enhancement module118, 112, 114, which then adapts and passes messages to the dataterminal 202, 204, 206 as described above. Additionally, instead ofreceiving messages at the main processing unit 208, 210, 212 from thedata terminal 202, 204, 206, the messages received at the data terminal202, 204, 206 are passed to the communication enhancement module 112,114, 118 before being un-adapted and passed to the main processingmodule 208, 210, 212 as discussed above. Accordingly, the communicationenhancement modules 112, 114, 118 can easily be added to new or existingSTANAG 4586 compliant MUCS 108 or UAVs 102, 104, 106.

FIG. 3 is flow diagram of an example method 300 of enhancingcommunication with the communication enhancement modules 112, 114, 116,118. One means of enhancing communication of a MUCS 108 and UAVs 102,104, 106 is to enable messages to be sent over a multi-hop route betweenthe MUCS 108 and a first UAV 102, 104, 106, via another UAV 102, 104,106. STANAG 4586 does not support UAV-to-UAV wireless links. Thus, UAVs102, 104, 106 and MUCS 108 using STANAG 4586 are restricted tocommunicating with each other over their respective UAV-to-MUCS link. Ifthe bandwidth of that UAV-to-MUCS link becomes degraded, communicationbetween the MUCS 108 and UAV 102, 104, 106 suffers.

The communication enhancement modules (CEMs) 112, 114, 116, 118,however, cooperate with one another to implement one or more UAV-to-UAVwireless links 111 among the UAVs 102, 104, 106 (block 302). Toestablish a UAV-to-UAV wireless link 111, the communication enhancementmodules 112, 114, 116, 118 direct their corresponding data terminals202, 204, 206 to send and receive messages in the frequency ranges ofthe data terminals 202, 204, 206 in other UAVs 102, 104, 106. Themessages sent and received by the data terminals 202, 204, 206 can beused to discover other communication enhancement modules 112, 114, 116,118 and to establish UAV-to-UAV links 111.

As an example, with reference to FIG. 2, the communication enhancementmodule 112 of the first UAV 102 can direct the data terminal 202 of thefirst UAV 102 to send a message (e.g., a discovery message) to thesecond UAV 104 (or any UAV within range) to establish a UAV-to-UAVwireless link 111. The message to establish a UAV-to-UAV link 111 can beaddressed to a specific UAV (e.g. the second UAV 104) that is likely tobe within range of the first UAV 102, or can be a generic broadcastmessage that is directed to any UAV that is within range. In an example,such a generic broadcast message can include information restricting theUAVs to which the message is directed, to the set of UAVs under controlof the same MUCS 108 that is controlling the first UAV 102. That is, themessage to establish a UAV-to-UAV link 111 can be directed to any UAVthat is being controlled by the MUCS 108 that is controlling the UAVsending the message. Thus, if other UAVs controlled by different MUCSare operating within communication range of the first UAV 102,UAV-to-UAV links 111 will not be established with those other UAVs.

The data terminal 204 of the second UAV 104 can receive the message andpass the message to the communication enhancement module 114 of thesecond UAV 104. The communication enhancement module 114 can then replyback to the first UAV 102 with an appropriate message to establish thewireless link 111. Notably, since the UAV-to-UAV link 111 is establishedbetween the communication enhancement modules 112, 114, control messagesrelated to establishing and maintaining the link 111 originate from andterminate at the communication enhancement modules 112, 114. The mainprocessing modules 210, 212 do not need to support, or even know about,the UAV-to-UAV link 111. Accordingly, the control messages can conformto a communication protocol that is specific to the communicationenhancement modules 112, 114, 118 and has been adopted thereby.

The UAVs 102, 104, 106 can also establish UAV-to-MUCS links 110 with theMUCS 108 in a manner in compliance with STANAG 4586. The UAV-to-MUCSlinks 110 formed between the MUCS 108 and the UAVs 102, 104, 106 alongwith the UAV-to-UAV links 111 formed amongst the UAVs 102, 104, 106 forma network among the UAVs 102, 104, 106, and MUCS 108.

The communication enhancement modules 112, 114, 118 share informationwith each other to identify and maintain multi-hop routes through thenetwork of UAVs 102, 104, and MUCS 108 (block 304). The communicationenhancement modules 112, 114, 118 can use these multi-hop routes tobypass a non-existent or bandwidth degraded UAV-to-MUCS link. Forexample, in the situation shown in FIG. 2, no UAV-to-MUCS link ispresent between the second UAV 104 and the MUCS 108 due to, for example,weather, geography, and/or enemy jamming. The second UAV 104 and thefirst UAV 102, however, have established a UAV-to-UAV link 111therebetween. The first UAV 102 and MUCS 108 have also established aUAV-to-MUCS link 110 therebetween. Through sharing of information, thecommunication enhancement modules 112, 114, 118 form a multi-hop routebetween the MUCS 108 and the second UAV 104 via the UAV-to-MUCS link 110between the MUCS 108 and the first UAV 102, and the UAV-to-UAV link 111between the first UAV 102 and the second UAV 104. The communicationenhancement modules 112, 114, 118 can use this multi-hop route to passSTANAG 4586 messages between the MUCS 108 and the second UAV 104, if aUAV-to-MUCS link between the second UAV 104 and the MUCS 108 is degradedor is not possible as shown in FIG. 2. The information shared, can beshared and stored by the communication enhancement modules 112, 114, 118in any appropriate form, such as in a routing table.

To enable a STANAG 4586 message to be sent over a multi-hop route, whichis not supported by STANAG 4586, the communication enhancement modules112, 114, 118 adapt the STANAG 4586 message before the message is sent,send the adapted message over the multi-hop route, and then undo theadaption upon receipt of the adapted message at the destination. Forexample, for a STANAG 4586 message being sent from the MUCS 108 to thesecond UAV 104, the main processing module 208 of the MUCS 108 cangenerate the STANAG 4586 message and include the second UAV 104 as thedestination in the STANAG 4586 message (block 305). The main processingmodule 208 can then pass the STANAG 4586 message to the communicationenhancement module 118 (block 306). The communication enhancement module118 can reference a routing table to identify the best route to thesecond UAV 104 (block 308). In the situation shown in FIG. 2, the bestroute to the second UAV 104 is over a multi-hop route through the firstUAV 102. Since this multi-hop route is not supported by STANAG 4586, thecommunication enhancement module 118 adapts the STANAG 4586 message forsending over the multi-hop route (block 310).

If a UAV-to-MUCS link with the second UAV 104 were available, and theUAV-to-MUCS link had sufficient bandwidth, the communication enhancementmodule 118 may determine that the best route is the UAV-to-MUCS link tothe second UAV 104. In such a situation, the communication enhancementmodule 118 can pass the STANAG 4586 message on to the data terminal 206without adaption (block 312). That is, the STANAG 4586 message generatedby the main processing module 208 can be passed on in an unmodified formto the data terminal 206. The data terminal 206 can then transmit theSTANAG 4586 message over the UAV-to-MUCS link where it is received bythe second UAV 104.

In examples where the STANAG 4586 message is adapted for transmissionover the multi-hop route, adapting the STANAG 4586 message can includecreating a tunneled message from the STANAG 4586 message. The tunneledmessage can have any appropriate form. In an example, the tunneledmessage is a form that requires low-overhead, such as the low-overheadrouting method described in co-pending U.S. patent application Ser. No.15/425,364, entitled “Low-Overhead Routing”, which is herebyincorporated herein by reference.

In any case, the STANAG 4586 message is adapted to a form correspondingto a message protocol to which the communication enhancement modules112, 114, 116, 118 have adopted, such that the communication enhancementmodule 114 at the first UAV 102 receives the adapted message andidentifies that the message is to-be-routed to the second UAV 104.Notably, the adapted message (and more broadly the message protocoladopted by the communication enhancement modules 112, 114) does not needto conform to the STANAG 4586 standard, as the adapted message is beingsent to, and received by, other communication enhancement modules 112,114, 118, not by the main processing modules 208, 210, 212. Afteradapting the STANAG 4586 message, the communication enhancement module118 passes the adapted message on to the data terminal 206 (block 314).The data terminal 206 transmits the adapted message over the UAV-to-MUCSlink 110 to the first UAV 102 (block 316).

The data terminal 202 at the first UAV 102 receives the adapted messageand passes the adapted message to the communication enhancement module112 of the first UAV 102 (block 318). The communication enhancementmodule 112 of the first UAV 102 identifies that the adapted message isdestined for the second UAV 104 (block 320). In response to identifyingthat the destination of the message is the second UAV 104, thecommunication enhancement module 112 of the first UAV 102 passes theadapted message back to the data terminal 202 for transmission overwireless link 111 to the second UAV 104 (block 322). The adapted messagepassed back to the data terminal 202 by the communication enhancementmodule 112 of the first UAV 102 can be identical to the adapted messagereceived from the MUCS 108, or can be a modified version thereof. In anycase, however, the adapted message is in a form corresponding to themessage protocol that the communication enhancement modules 112, 114,116, 118 have adopted. The adapted message from the communicationenhancement module 112 is then transmitted by the data terminal 202 ofthe first UAV 102 over the UAV-to-UAV link 111 (block 324).

The data terminal 204 of the second UAV 104 receives the adapted messageand passes the adapted message to the communication enhancement module114 of the second UAV 104 (block 326). This communication enhancementmodule 114 identifies that the adapted message is destined for thesecond UAV 104 and undoes the adaptations made by the communicationenhancement module 118 in the MUCS 108 as well as any adaptations madeby the communication enhancement module 112 in the first UAV 102 (block328). By undoing the adaptations, the communication enhancement module114 of the second UAV 104 re-generates the STANAG 4586 messageoriginally generated by the main processing module 208 of the MUCS 108.The re-generated STANAG 4586 message is passed from the communicationenhancement module 114 to the main processing module 212 of the secondUAV 104 (block 330). The main processing module 212 of the second UAV104 can then decode the STANAG 4586 message in accordance with STANAG4586 (block 332) as if the STANAG 4586 message had been sent over aUAV-to-MUCS link between the MUCS 108 and the second UAV 104 inaccordance with STANAG 4586.

The message protocol adopted by the communication enhancement modules112, 114, 116, 118 allows a communication enhancement module 112, 114,116, 118 receiving an adapted message to undo the adaptations andre-generate the original STANAG 4586 message. That is, a communicationenhancement module 112, 114, 116, 118 receiving an adapted message candetermine what the original STANAG 4586 message was from the adaptedmessage based on the message protocol adopted by the communicationenhancement modules 112, 114, 116, 118. Any suitable scheme ofindicating the original message in an adapted (e.g., tunneled message)can be used.

Advantageously, the adapted message can be sent, received, and routed onby the MUCS 108, the first UAV 102, and the second UAV 104 withoutrequiring interaction with their main processing modules 208, 210, 212.Thus, the main processing modules 208, 210, 212 do not need extensiveadaptation to enable the multi-hop route. Instead, the addedcommunication enhancement modules 112, 114, 118 interact with the mainprocessing modules 208, 210, 212 using their already included STANAG4586 interface.

Messages sent from the second UAV 104 to the MUCS 108 can similarly berouted through the first UAV 102 over the multi-hop route by thecommunication enhancement modules 112, 114, 118. In this direction, themain processing module 212 generates a STANAG 4586 message fortransmission over a point-to-point link to the MUCS 108. The mainprocessing module 212 passes the STANAG 4586 message to thecommunication enhancement module 114, which identifies that the bestroute to the MUCS 108 is via the multi-hop route through the first UAV102. The communication enhancement module 114 then adapts the STANAGmessage and passes the adapted message to the data terminal 204 fortransmission over the UAV-to-UAV link 111 to the first UAV 102.

The data terminal 202 of the first UAV 102 receives the adapted messageand passes the adapted message to the communication enhancement module112 of the first UAV 102. The communication enhancement module 112 ofthe first UAV 102 identifies the MUCS 108 as the destination of theadapted message and passes the adapted message back to the data terminal202 for transmission over UAV-to-MUCS link 110 to the MUCS 108. The dataterminal 206 of the MUCS 108 receives the adapted message and passes theadapted message to the communication enhancement module 118 of the MUCS108. The communication enhancement module 118 of the MUCS 108 undoes theadaptations to the message to re-generate the STANAG 4586 messageoriginally generated by the main processing module 212 of the second UAV104. The re-generated STANAG 4586 message is then passed to the mainprocessing module 208 of the MUCS 108 to be processed in the normalmanner thereby.

Although the multi-hop route in the example described above includes asingle UAV (the first UAV 102) between the source of a STANAG 4586message (e.g., the MUCS 108) and the destination of the STANAG 4586message (e.g., the second UAV 104), any number of UAVs can be disposedbetween the source and the destination if those UAVs have respectivecommunication enhancement modules that have established UAV-to-UAV linksas described herein. Accordingly, the multi-hop route can have more thanone hop (UAV) between the source and the destination.

In an example, the communication enhancement modules 112, 114, 116, 118can generate and pass synthetic STANAG 4586 compliant Data Link messagesto their corresponding main processing module 210, 212, 208 to fool themain processing module 210, 212, 208 into thinking there is a STANAG4586 compliant data link established with a UAV/MUCS 102, 104, 106, 108.It may be necessary to fool the main processing module 210, 212, 218,because if the main processing module 210, 212, 208 does not think thereis a STANAG 4586 compliant data link available to a UAV/MUCS 102, 104,106, 108, that main processing module 210, 212, 208 may not send anySTANAG 4586 messages to the UAV/MUCS 102, 104, 106, 108. Thus, in orderto utilize the multi-hop route created by the communication enhancementmodules 112, 114, 116, 118, it may be necessary to fool the mainprocessing module 210, 212, 218 into believing there is a STANAG 4586compliant data link with the UAV/MUCS 102, 104, 106, 108, so that themain processing module 210, 212, 208 sends and receives STANAG 4586messages to/from that UAV/MUCS 102, 104, 106, 108.

To fool the main processing modules 210, 212, 208, the communicationenhancement module 112, 114, 116, 118 coupled to the main processingmodule 210, 212, 208 can generate synthetic STANAG 4586 messages toindicate to the main processing module 210, 212, 208 that a STANAG 4586compliant UAV-to-MUCS link is available. For example, in the situationshown in FIG. 2, the communication enhancement module 118 can generatethe necessary STANAG 4586 messages to fool the main processing module208 of the MUCS 108 into believing it is establishing a STANAG 4586compliant data link between the MUCS 108 and the second UAV 104. TheSTANAG 4586 messages generated by the communication enhancement module118 can be generated as if the messages were being generated and sent bythe second UAV 104. The STANAG 4586 messages can then be passed by thecommunication enhancement module 118 to the main processing module 208of the MUCS 108 in sequence as necessary to fool the main processingmodule 208 into believing it is establishing a data link with the secondUAV 104. The communication enhancement module 114 can likewise generatesynthetic STANAG 4586 data link messages (as if the messages were fromthe MUCS 108) and pass them to the main processing module 212 of thesecond UAV 104 to fool that main processing module 212 into believing itis establishing a data link with the MUCS 108. Once this process iscompleted on both the second UAV 104 and the MUCS 108, their respectivemain processing modules 212, 208 will believe there is a STANAG 4586compliant data link established therebetween, when in fact no such datalink is present. The communication enhancement modules 114, 118 can alsogenerate the necessary STANAG 4586 data link messages thereafter tomaintain that belief of the STANAG 4586 data link.

Alternatively, some or all of the synthetic messages can be generated bythe communication enhancement module 112, 114, 116, 118 on the oppositeend of the faked data link. That is, the synthetic STANAG 4586 messagesfor the main processing module 118 of the MUCS 108 can be generated bythe communication enhancement module 114 of the second UAV 104 and sentover the multi-hop link from the second UAV 104 to the MUCS 108.Similarly, the synthetic STANAG 4586 message for the main processingmodule 212 of the second UAV 104 can be generated by the communicationenhancement module 118 of the MUCS 108 and sent from the MUCS 108 overthe multi-hop route to the second UAV 104.

In any case, the synthetic STANAG 4586 data link messages can includeany STANAG 4586 message for establishing, maintaining, or ending aSTANAG 4586 compliant data link. Example STANAG 4586 data link messagesinclude Data Link Discovery Messages, Data Link Command Messages, DataLink Status Messages, and Data Link Transition Messages as described inthe STANAG 4586 standard.

In an example, the communication enhancement modules 112, 114, 118 canmodify a real STANAG 4586 Data Link Status message to fool a mainprocessing module 210, 212, 208 into believing the parameters of anestablished data link are different than the parameters actually are.For example, the communication enhancement module 118 of the MUCS 108can modify a STANAG 4586 Data Link Status message from the second UAV104 so that the modified STANAG 4586 Data Link Status message reflects aparameter(s) of a multi-hop route to the second UAV 104, instead of aparameter of a UAV-to-MUCS link between the second UAV 104 and the MUCS108 (in a situation where a UAV-to-MUCS link is present between thesecond UAV 104 and the MUCS 108). Fooling the main processing module 210in this way may be beneficial to get the main processing module 210 toutilize the multi-hop route efficiently. Similar modifications can bemade for STANAG 4586 Data Link Status messages sent from the MUCS 108 tothe second UAV 104.

Other STANAG 4586 messages can be synthetically generated or modified ina similar manner by the communication enhancement modules 112, 114, 116,118 for other purposes.

The communication enhancement modules 112, 114, 116, 118 can also enableUAV-to-UAV communications. That is, two UAVs 102, 104, 106 havingcooperating communication enhancement modules therein can communicatewith each other. Messages sent between two or more UAVs can take anysuitable format, and the communication enhancement modules 112, 114,116, 118 can modify such a message, and route the message to thedestination UAV(s) 102, 104, 106 via the available communication links110, 111. UAV-to-UAV messages could include messages to coordinateflight paths, such as to avoid overlapping coverage areas, cover a widerarea, or to converge on an area for a joint task. Other UAV-to-UAVmessages could also be used.

Since conventional STANAG 4586 messages do not support UAV-to-UAVcommunications, a UAV 102, 104, 106 may have to be modified to includeadditional application layer software to enable UAV-to-UAVcommunications. In an example, however, the communication enhancementmodules 112, 114, 116, 118 can enable a first UAV 102 that includesapplication layer software to support UAV-to-UAV communications to sendcontrol messages to a second UAV 104 which does not include suchapplication layer software. To control such a second UAV 104, the mainprocessing module 210 of the first UAV 102 can generate a controlmessage instructing the second UAV 104 to take some action. Since STANAG4586 does not support UAV-to-UAV messages, the control message can takeany suitable format, including a format similar to a proper STANAG 4586message. The main processing module 210 of the first UAV 102 sends thecontrol message to the communication enhancement module 202 of the firstUAV 102. The communication enhancement module 202 can modify the messageif necessary to get the message into a form that will be understood bythe other communication enhancement modules 204, 206, 208. If themessage is already in a form that will be understood by the othercommunication enhancement modules 204, 206, 208, the communicationenhancement module 102 may not modify the message. In either case, thecommunication enhancement module 202 can send the message to the dataterminal 202 of the first UAV 102 for transmission over one or morecommunication links 110, 111 to the second UAV 104.

The message can be routed by the communication enhancement modules 112,114, 116, 118 as desired to arrive at the second UAV 104. The messagecan be received by the data terminal 204 of the second UAV 104 andpassed to the communication enhancement module 114 thereof. Thecommunication enhancement module 114 can modify the message, ifnecessary, so that the message has the format of a STANAG 4586 controlmessage sent from the MUCS 108. If the message already has a format of aSTANAG 4586 control message from the MUCS 108, the communicationenhancement module 114 need not modify the message. The communicationenhancement module 114 can then send the STANAG 4586 message to the mainprocessing module 114 of the second UAV 104. Since the message appearsas a STANAG 4586 message from the MUCS 108, the main processing module114 will decode the message and act on the message as it would if themessage were actually send by the MUCS 108. The control message caninclude any suitable payload, including an instruction to update aroute, waypoint, or the like for the second UAV 104. In this way, afirst UAV 102 having the capability of UAV-to-UAV communication cancontrol a second UAV 104 that lacks such a capability.

The communication enhancement modules 112, 114, 116, 118 can alsoprovide other communication enhancements, including adjusting whichlinks or routes a traffic flow is sent over based on available bandwidthof the links or routes, adjust a traffic flows bandwidth requirements byapplying QoS techniques such as header compression and filtering,pre-emptying lower priority flows to allow a higher-priority flow toutilize a link or route, coordinating among the UAVs that are sharing alink so that lower-priority flows will stop their transmissions to allowhigher priority flows from other UAVs to use the link. Notably, thesecommunication enhancements can be performed for STANAG 4586 messages ina manner transparent to the UAVs/MUCS 102, 104, 106, 108 by modifying aSTANAG 4586 message before transmission and undoing the modifications atthe destination as described herein.

As mentioned above, each communication enhancement module 112, 114, 116,118 can be a software-tool that is loaded onto a MUCS 108 or UAV 102,104, 106, or the communication enhancement module 112, 114, 116, 118 canbe a hardware appliance with appropriate software that is installed in aMUCS 108 or UAV 102, 104, 106. In any case the communication enhancementmodule 112, 114, 116, 118 can be coupled or otherwise linked to the mainprocessing module 210, 212, 208 and the data terminal 202, 204, 206 inits MUCS 108 or UAV 102, 104, 106.

FIG. 4 is a block diagram of an example UAV 102 that includes acommunication enhancement module 112 that is a software tool. The UAV102 includes a propulsion unit 402 to propel the UAV 102. Anyappropriate propulsion unit 402 can be used including one or moreelectric motors or fuel engines and propellers, jet engines, and/orducted fan.

The UAV 102 also includes a main processing module 210 that performs thegeneral processing for the UAV 102. The main processing module 210includes one or more processing devices 404 for executing instructions406. The one or more processing devices 404 can include ageneral-purpose processor or a special purpose processor. Theinstructions 406 are stored (or otherwise embodied) on or in anappropriate storage medium or media 408 (such as flash or othernon-volatile memory) from which the instructions 406 are readable by theprocessing device(s) 404 for execution thereby. The main processingmodule 210 also includes memory 410 that is coupled to the processingdevice(s) 404 for storing instructions (and related data) duringexecution by the processing device(s) 404. Memory 410 comprises, in oneimplementation, any suitable form of random access memory (RAM) nowknown or later developed, such as dynamic random-access memory (DRAM).In other implementations, other types of memory are used.

The instructions 406 include the main processing module instructions 410which, when executed by the one or more processing devices 404, causethe one or more processing devices 404 to perform the actions of themain processing module 210 described herein. The instructions 406 alsoinclude the communication enhancement module 112 software tool loadedthereon. The communication enhancement module 112 includes instructionswhich, when executed by the one or more processing devices 404, causethe one or more processing devices 404 to perform the actions of thecommunication enhancement module 112 described herein. The instructions406 also direct information to be passed between the communicationenhancement module 112 and the main processing module 410 as describedherein.

In an example, the communication enhancement module 112 or a portionthereof can be stored or otherwise embodied on a computer readablemedium that is distinct from the UAV 102 and can be loaded onto the mainprocessing module 210 to implement the communication enhancement module112 thereon. The computer readable media on which the communicationenhancement module 112 are stored can be any suitable computer readablemedia such as a magnetic media such as a hard disk drive (HDD), opticalmedia such as a CD, DVD, Blu-Ray disk, or a non-volatile electric mediasuch as a solid-state drive (SDD), flash media, or EEPROM. Such computerreadable media can be standalone media (e.g., a USB stick or CD) or canbe computer readable media within a computing device (e.g., a server ornetwork accessible storage).

The main processing module 210 is coupled to the propulsion unit 402 toprovide commands thereto and receive information from sensors thereof.The main processing module 210 is also coupled to a data terminal 202,which includes one or more wireless transceivers for transmitting andreceiving wireless signals with a MUCS 108 and one or more UAVs 104, 106as described herein. The UAV 102 can also include one or more payloadelements 218 coupled to the main processing module 210 as describedherein.

FIG. 5 is a block diagram of another example UAV 104 that includes acommunication enhancement module 114 that is a hardware with softwareappliance, installed in the UAV 104. Similar to UAV 102 of FIG. 4, theUAV 104 includes a propulsion unit 502 to propel the UAV 104. Anyappropriate propulsion unit 502 can be used including one or moreelectric motors or fuel engines and propellers, jet engines, and/orducted fan.

The UAV 104 also includes a main processing module 212 that performs thegeneral processing for the UAV 104. The main processing module 212includes one or more processing devices 504 for executing instructions506. The one or more processing devices 504 can include ageneral-purpose processor or a special purpose processor. Theinstructions 506 are stored (or otherwise embodied) on or in anappropriate storage medium or media 508 (such as flash or othernon-volatile memory) from which the instructions 506 are readable by theprocessing device(s) 504 for execution thereby. The instructions 506include the main processing module instructions 510 which, when executedby the one or more processing devices 504, cause the one or moreprocessing devices 504 to perform the actions of the main processingmodule 212 described herein. The main processing module 212 alsoincludes memory 509 that is coupled to the processing device(s) 504 forstoring instructions (and related data) during execution by theprocessing device(s) 504. Memory 509 comprises, in one implementation,any suitable form of random access memory (RAM) now known or laterdeveloped, such as dynamic random-access memory (DRAM). In otherimplementations, other types of memory are used.

The main processing module 212 is coupled to the propulsion unit 502 toprovide commands thereto and receive information from sensors thereof.The main processing module 212 is also coupled to the communicationenhancement module 114, which is an appliance installed in the UAV 104.The communication enhancement module 114 includes one or more processingunits 511, which are distinct from the one or more processing devices504 of the main processing module. The one or more processing devices511 can include a general-purpose processor or a special purposeprocessor. The communication enhancement module 114 also includesinstructions 512, which are stored (or otherwise embodied) on or in anappropriate storage medium or media 514 (such as flash or othernon-volatile memory) from which the instructions 512 are readable by theprocessing device(s) 510 for execution thereby. The instructions 512include the instructions which, when executed by the one or moreprocessing devices 511, cause the one or more processing devices 511 toperform the actions of the communication enhancement module 114described herein. The communication enhancement module 114 also includesmemory 516 that is coupled to the processing device(s) 511 for storinginstructions (and related data) during execution by the processingdevice(s) 511. Memory 516 comprises, in one implementation, any suitableform of random access memory (RAM) now known or later developed, such asdynamic random-access memory (DRAM). In other implementations, othertypes of memory are used.

The communication enhancement module 114 is coupled to the data terminal204, which includes one or more wireless transceivers for transmittingand receiving wireless signals with a MUCS 108 and one or more UAVs 102,106 as described herein. The UAV 104 can also include one or morepayload elements 220 coupled to the main processing module 212 asdescribed herein.

Although the example UAVs 102, 104 shown in FIGS. 4, 5 include asoftware tool and a hardware-with-software appliance respectively, theseare merely examples. The communication enhancement module 112, 114, 116,118 of the UAVs 102, 104, 106 or MUCS 108 can be either a software toolor a hardware with software appliance.

What is claimed is:
 1. A communication enhancement module for anunmanned aerial vehicle (UAV) or a multi-UAV control system (MUCS), thecommunication enhancement module comprising: a computer readable mediumhaving instructions thereon, the instructions, when executed by one ormore processing devices, cause the one or more processing devices to:receive a STANAG 4586 message from an upstream module, the STANAG 4586message indicating that a second UAV or a MUCS is its destination;identify a multi-hop path to the second UAV or the MUCS via at least oneother communication enhancement module in a first UAV; determine whethera point-to-point wireless link or the multi-hop path is a better path tothe second UAV or the MUCS; if the point-to-point wireless link is thebetter path, send a message based on the STANAG 4586 message over thepoint-to-point wireless link to the second UAV or the MUCS; if themulti-hop path is the better path: adapt the STANAG 4586 message tocreate a modified message having a format corresponding to thecommunication enhancement modules; and send the modified message to acommunication enhancement module of the first UAV for directing towardthe second UAV or the MUCS.
 2. The communication enhancement module ofclaim 1, wherein adapt the STANAG 4586 message includes create atunneled message.
 3. The communication enhancement module of claim 1,wherein send a message based on the STANAG 4586 message over thepoint-to-point wireless link includes send the STANAG 4586 message in anunmodified form to over the point-to-point wireless link.
 4. Thecommunication enhancement module of claim 1, wherein the upstream moduleis one of a vehicle specific module for an unmanned aerial vehicle (UAV)or a UAV control system.
 5. The communication enhancement module ofclaim 1, wherein, send a message based on the STANAG 4586 message overthe point-to-point wireless link includes send a message to a dataterminal, which wirelessly transmits the message to a data terminal ofthe second UAV or MUCS, wherein, send the modified message to acommunication enhancement module includes send the modified message to adata terminal, which transmits the modified message to a data terminalof the first UAV.
 6. The communication enhancement module of claim 1,wherein the instructions cause the one or more processing devices to:generate a synthetic STANAG 4586 message to fool the upstream moduleinto believing there is a STANAG 4586 compliant data link with thesecond UAV or MUCS.
 7. The communication enhancement module of claim 1,wherein the instructions cause the one or more processing devices to:modify a STANAG 4586 data link message to fool the upstream module intobelieving at least one parameter of a STANAG 4586 compliant data link isdifferent than the parameter really is.
 8. A method for enhancingcommunication for one or more unmanned aerial vehicles (UAVs), themethod comprising: receiving, at a first communication enhancementmodule of a first UAV of the one or more UAVs, a STANAG 4586 messagefrom an upstream module in the first UAV, wherein the STANAG 4586message indicates a MUCS as its destination; identifying a multi-hoppath to the MUCS via at least one other communication enhancement moduleof at least one other UAV; determining whether a point-to-point wirelesslink or the multi-hop path is a better path to the MUCS; if apoint-to-point wireless link is a better path, sending a message basedon the STANAG 4586 message over the point-to-point wireless link to theMUCS; if the multi-hop path is a better path: modifying the STANAG 4586message to create a modified message having a format corresponding tothe communication enhancement modules; and sending the modified messageto the at least one other communication enhancement module on themulti-hop path for directing toward the MUCS.
 9. The method of claim 8,wherein modifying the STANAG 4586 message includes creating a tunneledmessage.
 10. The method of claim 8, wherein sending a message based onthe STANAG 4586 message over the point-to-point wireless link includessending the STANAG 4586 message in an unmodified form over thepoint-to-point wireless link.
 11. The method of claim 8, wherein theupstream module is a vehicle specific module for the first UAV.
 12. Themethod of claim 8, wherein sending a message based on the STANAG 4586message over the point-to-point wireless link includes sending a messageto a data terminal of the first UAV, which wirelessly transmits themessage to a data terminal of the MUCS, wherein sending the modifiedmessage to at least one other communication enhancement module of atleast one other UAV includes sending the modified message to the dataterminal of the first UAV, which transmits the modified message to adata terminal of the at least one other UAV.
 13. The method of claim 8,comprising: generating a synthetic STANAG 4586 message to fool theupstream module into believing there is a STANAG 4586 compliant datalink with the MUCS.
 14. The method of claim 8, comprising: modifying aSTANAG 4586 data link message to fool the upstream module into believingat least one parameter of a STANAG 4586 compliant data link is differentthan the parameter really is.
 15. An unmanned aerial vehicle (UAV)comprising: a propulsion system to propel the UAV in flight; and acommunication enhancement module, the communication enhancement modulecomprising: one or more processing devices; a computer readable mediumcoupled to the one or more processing devices, the computer readablemedium having instructions thereon, the instructions, when executed bythe one or more processing devices, cause the one or more processingdevices to: receive a STANAG 4586 message from an upstream module, theSTANAG 4586 message indicating that a MUCS is its destination; identifya multi-hop path to the MUCS via at least one other communicationenhancement module in another UAV; determine whether a point-to-pointwireless link or the multi-hop path is a better path to the MUCS; if thepoint-to-point wireless link is the better path, send a message based onthe STANAG 4586 message over the point-to-point wireless link to theMUCS; if the multi-hop path is the better path: adapt the STANAG 4586message to create a modified message having a format corresponding tothe communication enhancement modules; and send the modified message toa communication enhancement module of the other UAV for directing towardthe MUCS.
 16. The UAV of claim 15, wherein adapt the STANAG 4586 messageincludes create a tunneled message.
 17. The UAV of claim 15, whereinsend a message based on the STANAG 4586 message over the point-to-pointwireless link includes send the STANAG 4586 message in an unmodifiedform over the point-to-point wireless link.
 18. The UAV of claim 15,wherein the upstream module is a vehicle specific module.
 19. The UAV ofclaim 15, wherein send a message based on the STANAG 4586 message overthe point-to-point wireless link includes send a message to a dataterminal, which wirelessly transmits the message to a data terminal ofthe MUCS, wherein send the modified message to a communicationenhancement module includes send the modified message to a dataterminal, which transmits the modified message to a data terminal of theother UAV.
 20. The UAV of claim 15, wherein the instructions cause theone or more processing devices to: generate a synthetic STANAG 4586message to fool the upstream module into believing there is a STANAG4586 compliant data link with the MUCS.
 21. The UAV of claim 15, whereinthe instructions cause the one or more processing devices to: modify aSTANAG 4586 data link message to fool the upstream module into believingat least one parameter of a STANAG 4586 compliant data link is differentthan the parameter really is.